Multi-part parsing in a network device

ABSTRACT

A network device for processing data on a data network includes a plurality of ports, configured to receive data from a data network and to send processed data to the data network, a memory management unit configured store data on and retrieve data from the memory and a multi-part parser configured to parse the data received. The multi-part parser comprises several parsing blocks configured to serially parse the data, with each block designated to parse particular values and where each block but a first block receives parsed data from a prior block with the particular values at a zero offset position.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority of U.S. Provisional Patent ApplicationSer. No. 60/653,953, filed on Feb. 18, 2005. The subject matter of thisearlier filed application is hereby incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a network device for processing data ina network and more particularly to parsing of data received by a networkdevice that allows for enhanced processing speeds and data handling.

2. Description of the Related Art

A network may include one or more network devices, such as Ethernetswitches, each of which includes several modules that are used toprocess information that is transmitted through the device.Specifically, the device may include port interface modules, designed tosend and receive data over a network, a Memory Management Unit (MMU), tostore that data until it is forwarded or further processed andresolution modules, that allow the data to be reviewed and processedaccording to instructions. The resolution modules include switchingfunctionalities for determining to which destination port data should bedirected. One of the ports on the network device may be a CPU port thatenables the device to send and receive information to and from externalswitching/routing control entities or CPUs.

Many network devices operate as Ethernet switches, where packets enterthe device from multiple ports, where switching and other processing areperformed on the packets. Thereafter, the packets are transmitted to oneor more destination ports through the MMU. The MMU enables sharing ofpacket buffer among different ports while providing resource guaranteesfor every ingress port, egress port and class of service queue.

However, many of these prior art network devices do not have sufficienthandling capacity and often these prior art devices are linked togetherto provide greater flexibility and the ability to handle greaterthroughput. Combining these prior art devices in linked combinationsproduces other problems that must be addressed, that may not need to beconsidered in a single network device. One issue that arises occurs whenmultiple types of data must be parsed and analyzed and there is a needto provide enhanced parsing and analysis to compensate for problems thatcan occur.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunder-standing of the invention and are incorporated in and constitute apart of this specification, illustrate embodiments of the invention thattogether with the description serve to explain the principles of theinvention, wherein:

FIG. 1 illustrates a network device in which an embodiment of thepresent invention may be implemented;

FIG. 2 illustrates a block diagram illustrating the communication usingports of the network device, according to an embodiment of the instantinvention;

FIG. 3 illustrates memory structures to be used with the network device,with FIG. 3 a illustrating the shared memory that is external to thenetwork device and FIG. 3 b illustrating the Cell Buffer Pool of theshared memory architecture;

FIG. 4 illustrates buffer management mechanisms that are used by thememory management unit to impose resource allocation limitations andthereby ensure fair access to resource;

FIG. 5 illustrates a two stage parser, according to certain embodimentsof the present invention;

FIG. 6 illustrates another parser for use with interconnected port,according to certain embodiments of the present invention;

FIG. 7 illustrates a result matcher, according to certain embodiments ofthe present invention;

FIG. 8 illustrates a configuration of an egress port arbitrationimplemented in the present invention;

FIG. 9 illustrates the stages of the multi-part parser, according to oneembodiment of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Reference will now be made to the preferred embodiments of the presentinvention, examples of which are illustrated in the accompanyingdrawings.

FIG. 1 illustrates a network device, such as a switching chip, in whichan embodiment the present invention may be implemented. Device 100includes port interface modules 112 and 113, a MMU 115, an ingress andegress module 130 and a search engine 120. The ingress and egress module130 parses the data received and performs look ups based on the parseddata using the search engine 120. The primary function of MMU 115 is toefficiently manage cell buffering and packet pointer resources in apredictable manner, even under severe congestion scenarios. Throughthese modules, packet modification can occur and the packet can betransmitted to an appropriate destination port.

According to several embodiments, the device 100 may also include oneinternal fabric high speed port, for example a HiGig™ or high speedport, 108, one or more external Ethernet ports 109 a-109 x, and a CPUport 110. High speed port 108 is used to interconnect various networkdevices in a system and thus form an internal switching fabric fortransporting packets between external source ports and one or moreexternal destination ports. As such, high speed port 108 may notexternally visible outside of a system that includes the multipleinterconnected network devices. CPU port 110 is used to send and receiveinformation to and from external switching/routing control entities orCPUs. According to an embodiment of the invention, CPU port 110 may beconsidered as one of external Ethernet ports 109 a-109 x. Device 100interfaces with external/off-chip CPUs through a CPU processing module111, such as a CMIC, which interfaces with a PCI bus that connectsdevice 100 to an external CPU.

In addition, the search engine module 120 may be composed of additionalsearch engine modules, 122, 124 and 126, that are used to performparticular look ups that are used in the characterization andmodification of data being processed by the network device 100.Likewise, the ingress and egress module 130 also includes additionalmodules that are directed to parsing data received from the internalfabric high speed port 134 and the other ports 138, with other modules132 and 136 for forwarding data back to the ports of the network device.The two parsers are discussed in greater detail below.

Network traffic enters and exits device 100 through external Ethernetports 109 a-109 x. Specifically, traffic in device 100 is routed from anexternal Ethernet source port to one or more unique destination Ethernetports. In one embodiment of the invention, device 100 supports twelvephysical Ethernet ports 109, each of which can operate in 10/100/1000Mbps speed and one high speed port 108 which operates in either 10 Gbpsor 12 Gbps speed.

The structure of the physical ports 112 are further illustrated in FIG.2. A series of serializing/deserializing modules 103 send and receivedata, where data received as each port is managed by a port manager102A-L. The series of port managers have a timing generator 104 and abus agent 105 that facilitate their operation. The data received andtransmitted to a port information base so that the flow can bemonitored. It is noted that high speed port 108 has similarfunctionalities but does not require as many elements since only oneport is being managed but operates at a higher speed.

In an embodiment of the invention, device 100 is built around a sharedmemory architecture, as shown in FIGS. 3 a-3 b wherein MMU 115 enablessharing of a packet buffer among different ports while providing forresource guarantees for every ingress port, egress port and class ofservice queue associated with each egress port. FIG. 3 a illustrates theshared memory architecture of the present invention. Specifically, thememory resources of device 100 include a Cell Buffer Pool (CBP) memory302 and a Transaction Queue (XQ) memory 304. CBP memory 202 is anoff-chip resource that is made of, according to some embodiments, 4 DRAMchips 306 a-306 d. According to an embodiment of the invention, eachDRAM chip has a capacity of 288 Mbits, wherein the total capacity of CBPmemory 302 is 122 Mbytes of raw storage. As shown in FIG. 3 b, CBPmemory 302 is divided into 256K 576-byte cells 308 a-308 x, each ofwhich includes a 32 byte header buffer 310, up to 512 bytes for packetdata 312 and 32 bytes of reserved space 314. As such, each incomingpacket consumes at least one full 576 byte cell 308. Therefore in anexample where an incoming includes a 64 byte frame, the incoming packetwill have 576 bytes reserved for it even though only 64 bytes of the 576bytes is used by the frame.

Returning to FIG. 3 a, XQ memory 304 includes a list of packet pointers316 a-316 x into CBP memory 302, wherein different XQ pointers 316 maybe associated with each port. A cell count of CBP memory 302 and apacket count of XQ memory 304 is tracked on an ingress port, egress portand class of service basis. As such, device 100 can provide resourceguarantees on a cell and/or packet basis.

Once a packet enters device 100 on a source port 109, the packet istransmitted to parser 130 for processing. During processing, packets oneach of the ingress and egress ports share system resources 302 and 304.In specific embodiments, two separate 64 byte bursts of packets areforwarded to the MMU from the local ports and the High speed port. FIG.4 illustrates buffer management mechanisms that are used by MMU 115 toimpose resource allocation limitations and thereby ensure fair access toresources. MMU 115 includes an ingress backpressure mechanism 404, ahead of line mechanism 406 and a weighted random early detectionmechanism 408. The Ingress backpressure mechanism 404 supports losslessbehaviour and manages buffer resources fairly across ingress ports. Headof line mechanism 406 supports access to buffering resources whileoptimizing throughput in the system. Weighted random early detectionmechanism 408 improves overall network throughput.

The ingress backpressure mechanism 404 uses packet or cell counters totrack the number of packets or cells used on an ingress port basis. Theingress backpressure mechanism 404 includes registers for a set of 8individually configurable thresholds and registers used to specify whichof the 8 thresholds are to be used for every ingress port in the system.The set of thresholds include a limit threshold 412, a discard limitthreshold 414 and a reset limit threshold 416. If a counter associatedwith the ingress port packet/cell usage rises above discard limitthreshold 414, packets at the ingress port will be dropped. Based on thecounters for tracking the number of cells/packets, a pause flow controlis used to stop traffic from arriving on an ingress port that have usedmore than its fair share of buffering resources, thereby stoppingtraffic from an offending ingress port and relieving congestion causedby the offending ingress port.

Specifically, each ingress port keeps track of whether or not it is inan ingress backpressure state based on ingress backpressure countersrelative to the set of thresholds. When the ingress port is in ingressbackpressure state, pause flow control frames with a timer value of(0xFFFF) are periodically sent out of that ingress port. When theingress port is no longer in the ingress backpressure state, the pauseflow control frame with a timer value of 0x00 is sent out of the ingressport and traffic is allowed to flow again. If an ingress port is notcurrently in an ingress backpressure state and the packet counter risesabove limit threshold 412, the status for the ingress port transitionsinto the ingress backpressure state. If the ingress port is in theingress backpressure state and the packet counter falls below resetlimit threshold 416, the status for the port will transition out of thebackpressure state.

The head of line mechanism 406 is provided to support fair access tobuffering resources while optimizing throughput in the system. The headof line mechanism 406 relies on packet dropping to manage bufferingresources and improve the overall system throughput. According to anembodiment of the invention, the head of line mechanism 406 uses egresscounters and predefined thresholds to track buffer usage on a egressport and class of service basis and thereafter makes decisions to dropany newly arriving packets on the ingress ports destined to a particularoversubscribed egress port/class of service queue. Head of linemechanism 406 supports different thresholds depending on the color ofthe newly arriving packet. Packets may be colored based on metering andmarking operations that take place in the ingress module and the MMUacts on these packets differently depending on the color of the packet.

According to an embodiment of the invention, head of line mechanism 406is configurable and operates independently on every class of servicequeue and across all ports, including the CPU port. Head of linemechanism 406 uses counters that track XQ memory 304 and CBP memory 302usage and thresholds that are designed to support a static allocation ofCBP memory buffers 302 and dynamic allocation of the available XQ memorybuffers 304. A discard threshold 422 is defined for all cells in CBPmemory 302, regardless of color marking. When the cell counterassociated with a port reaches discard threshold 422, the port istransition to a head of line status. Thereafter, the port may transitionout of the head of line status if its cell counter falls below a resetlimit threshold 424.

For the XQ memory 304, a guaranteed fixed allocation of XQ buffers foreach class of service queue is defined by a XQ entry value 430 a-430 h.Each of XQ entry value 430 a-430 h defines how many buffer entriesshould be reserved for an associated queue. For example, if 100 bytes ofXQ memory are assigned to a port, the first four class of service queuesassociated with XQ entries 430 a-430 d respectively may be assigned thevalue of 10 bytes and the last four queues associated with XQ entries430 d-430 h respectively may be assigned the value of 5 bytes.

According to an embodiment of the invention, even if a queue does notuse up all of the buffer entries reserved for it according to theassociated XQ entry value, the head of line mechanism 406 may not assignthe unused buffer to another queue. Nevertheless, the remainingunassigned 40 bytes of XQ buffers for the port may be shared among allof the class of service queues associated with the port. Limits on howmuch of the shared pool of the XQ buffer may be consumed by a particularclass of service queue is set with a XQ set limit threshold 432. Assuch, set limit threshold 432 may be used to define the maximum numberof buffers that can be used by one queue and to prevent one queue fromusing all of the available XQ buffers. To ensure that the sum of XQentry values 430 a-430 h do not add up to more than the total number ofavailable XQ buffers for the port and to ensure that each class ofservice queue has access to its quota of XQ buffers as assigned by itsentry value 430, the available pool of XQ buffer for each port istracked using a port dynamic count register 434, wherein the dynamiccount register 434 keeps track of the number of available shared XQbuffers for the port. The initial value of dynamic count register 434 isthe total number of XQ buffers associated with the port minus a sum ofthe number of XQ entry values 430 a-430 h. Dynamic count register 434 isdecremented when a class of service queue uses an available XQ bufferafter the class of service queue has exceeded its quota as assigned byits XQ entry value 430. Conversely, dynamic count register 434 isincremented when a class of service queue releases a XQ buffer after theclass of service queue has exceeded its quota as assigned by its XQentry value 430.

When a queue requests XQ buffer 304, head of line mechanism 406determines if all entries used by the queue is less than the XQ entryvalue 430 for the queue and grants the buffer request if the usedentries are less then the XQ entry value 430. If however, the usedentries are greater than the XQ entry value 430 for the queue, head ofline mechanism 406 determines if the amount requested is less than thetotal available buffer or less then the maximum amount set for the queueby the associated set limit threshold 432. Set limit threshold 432 is inessence a discard threshold that is associated with the queue,regardless of the color marking of the packet. As such, when the packetcount associated with the packet reaches set limit threshold 432, thequeue/port enters into a head of line status. When head of linemechanism 406 detects a head of line condition, it sends an updatestatus so that packets can be dropped on the congested port.

However, due to latency, there may be packets in transition between theMMU 115 and the ports and when the status update is sent by head of linemechanism 406. In this case, the packet drops may occur at MMI 115 dueto the head of line status. In an embodiment of the invention, due tothe pipelining of packets, the dynamic pool of XQ pointers is reduced bya predefined amount. As such, when the number of available XQ pointersis equal to or less than the predefined amount, the port is transitionto the head of line status and an update status is sent to by MMU 115 tothe ports, thereby reducing the number of packets that may be dropped byMMU 115. To transition out of the head of line status, the XQ packetcount for the queue must fall below a reset limit threshold 436.

It is possible for the XQ counter for a particular class of servicequeue to not reach set limit threshold 432 and still have its packetdropped if the XQ resources for the port are oversubscribed by the otherclass of service queues. In an embodiment of the invention, intermediatediscard thresholds 438 and 439 may also be defined for packetscontaining specific color markings, wherein each intermediate discardthreshold defines when packets of a particular color should be dropped.For example, intermediate discard threshold 438 may be used to definewhen packets that are colored yellow should be dropped and intermediatediscard threshold 439 may be used to define when packets that arecolored red should be dropped. According to an embodiment of theinvention, packets may be colored one of green, yellow or red dependingon the priority level assigned to the packet. To ensure that packetsassociated with each color are processed in proportion to the colorassignment in each queue, one embodiment of the present inventionincludes a virtual maximum threshold 440. Virtual maximum threshold 440is equal to the number of unassigned and available buffers divided bythe sum of the number of queues and the number of currently usedbuffers. Virtual maximum threshold 440 ensures that the packetsassociated with each color are processed in a relative proportion.Therefore, if the number of available unassigned buffers is less thanthe set limit threshold 432 for a particular queue and the queuerequests access to all of the available unassigned buffers, head of linemechanism 406 calculates the virtual maximum threshold 440 for the queueand processes a proportional amount of packets associated with eachcolor relative to the defined ratios for each color.

To conserve register space, the XQ thresholds may be expressed in acompressed form, wherein each unit represents a group of XQ entries. Thegroup size is dependent upon the number of XQ buffers that areassociated with a particular egress port/class of service queue.

Weighted random early detection mechanism 408 is a queue managementmechanism that preemptively drops packets based on a probabilisticalgorithm before XQ buffers 304 are exhausted. Weighted random earlydetection mechanism 408 is therefore used to optimize the overallnetwork throughput. Weighted random early detection mechanism 408includes an averaging statistic that is used to track each queue lengthand drop packets based on a drop profile defined for the queue. The dropprofile defines a drop probability given a specific average queue size.According to an embodiment of the invention, weighted random earlydetection mechanism 408 may defined separate profiles on based on aclass of service queue and packet.

As illustrated in FIG. 1, the MMU 115 receives packet data for storagefrom the parser 130. As discussed above, the ingress and egress module130 includes a two stage parser, where that portion is illustratedschematically in FIG. 5. The data are received at ports 501 of thenetwork device, as discussed above. Data may also be received throughthe CMIC 502, where that data is passed to an ingress CMIC interface503. The interface acts to convert the CMIC data from a CMIC-bus formatto an ingress data format. In one embodiment, the data is converted from45-bit to 172-bit format, such that the latter format includes 128-bitdata, 20-bit control and possibly a 24-bit High speed header. The dataare thereafter sent in 64-byte bursts to the ingress arbiter 504.

The ingress arbiter 504 receives data from the ports 501 and the ingressCMIC interface 503, and multiplexes those inputs based on time divisionmultiplexing arbitration. Thereafter, the data are sent to the MMU 510,where any High speed header is removed and the format is set to a MMUinterface format. Packet attributes are checked, such as end-to-end,Ingress Back Pressure (IBP) or Head of Line (HOL) packets. In addition,the first 128 bytes of data are snooped and the High speed header ispassed to the parser ASM 525. If the burst of data received contains anend marker, the CRC result and packet length are sent to the resultmatcher 515. Also, the packet length is estimated from the burst lengthand a 16-bit packet ID is generated for debugging purposes.

The parser ASM 525 converts the 64 byte data burst, at 4 cycles perburst, into 128-byte burst, at 8 cycles per burst. The 128-byte burstdata is forwarded to both the tunnel parser 530 and the parser FIFO 528at the same time to maintain the same packet order. The tunnel parser530 determines whether any type of tunnel encapsulation, including MPLSand IP tunnelling, is being employed. In addition, the tunnel parseralso checks for outer and inner tags. Through the parsing process, thesession initiated protocol (SIP) is provided for subnet based VLAN,where the SIP parsing occurs if the packet is an address resolutionprotocol (ARP), reverse ARP (RARP) or IP packet. A trunk port grid ID isalso constructed based on the source trunk map table, unless there is notrunking or if the trunk ID is obtained from the High speed header.

The tunnel parser 530 works with the tunnel checker 531. The tunnelchecker checks the checksum of the IP header, and characteristics of UDPtunnelling and IPv6 over IPv4 packets. The tunnel parser 530 utilizesthe search engine 520 to determine the tunnel type through preconfiguredtables.

The parser FIFO 528 stores 128 bytes of packet headers and 12 bytes ofHigh speed headers, that is parsed again by the deep parser 540. Theheader bytes are stored while the search engine completes a search andis ready for the deeper search. Other attributes are also maintained bythe FIFO, such as valid header length, High speed header status and thepacket ID. The deep parser 540 provides three different types of data,including search results from the search engine 520 that are “flowthrough,” inner parser results and High speed module header. Specialpacket types are determined and passed along to the search engine. Thedeep parser 540 reads the data from the parser FIFO, where pre-definedfields are parsed. The search engine provides lookup results based onthe values passed to the search engine, where the packet ID is checkedto maintain packet order.

The deep parser 540 also uses the protocol checker 541 to check theinner IP header checksum, check for denial of service attack attributes,errors in the High speed module header and perform a martian check. Thedeep parser also works with the field processor parser 542, to parsepredefined fields and user defined fields. The predefined fields arereceived from the deep parser. These fields include MAC destinationaddress, MAC source address, inner and outer tags, Ether type, IPdestination and source addresses, Type of Service, IPP, IP flags, TDS,TSS, TTL, TCP flags and flow labels. User defined fields are alsoparsible, up to 128-bytes of packet header.

As discussed above, the data that is received on the High speed port istreated separately from other data received on the local ports. Asillustrated in FIG. 1, High speed port 108 has its own buffers and dataflows from the port to its own parser 134. The High speed parser isillustrated in greater detail than FIG. 6. The structure is similar tothe two stage parser, illustrated in FIG. 5, with several differences.Data received at the High speed port 601 is forwarded to the High speedport assembler 604. The assembler receives the data and High speedheader in 64 byte bursts, with a similar format as used for the localports. The data are sent to the MMU 610 without the High speed headerand in a MMU interface format.

The first 128 bytes of the data is snooped and sent, along with the Highspeed header, to the deep parser 640. With similarity to the two stageparser, end-to-end message are checked, with the parsed results beingsent in a side band. Also similarly, the CRC and packet lengths arechecked and the results are forwarded to the result matcher 615. Inaddition, a 16 bit packet ID is generated for use in debugging andtracking the flow of the packet.

The High speed version of the deep parser 640 is a subset of the twostage deep parser 540, and performs similar functions. There is,however, no pass through of information from the search engine 620, itcannot skip the MPLS header and parse the payload only and does not senddeep data to the search engine. In function, the High speed version ofthe FP parser 642 is the same as the FP parser 542 discussed above.

The result matcher is illustrated in greater detail in FIG. 7. It isnoted that the result matcher may be used commonly between the parsersor each parser may utilize its own result matcher. In the embodimentillustrated, both types of ports 710 & 720 receive data and forwardquantities to the result checker through the actions of the ingressassembler 715 and the ingress arbiter 725. The quantities include portnumber, presence of EOF, the CRC and the packet length. The resultmatcher acts as a series of FIFOs to match search results through theuse of the search engine 705. The tag and the MIB event are matched withthe packet length and the CRC status on a per port basis. The searchresults are provided every eight cycles for a network port and eightcycles for the high speed port. The structure allows for results to bestored in the result matcher per port if there is a delay that is longerthan the incoming packet time and awaiting the end of packet resultswhen the search delay is shorter than the incoming packet time.

After the process of parsing and evaluating of data received, aforwarding decision is made with regard to the received information. Theforwarding decision is generally made as to what destination port thepacket data should be sent to, although the decision can be made to dropa packet or forward a packet to a CPU or other controller through theCMIC 111. On egress, the packet is modified based on the parsing andevaluation of the network device. Such modification can include tagging,modification of header information or addition of a module header, ifthe egress port is the High speed port. The modification is performed ona cell basis to avoid delays in the forwarding of the packet data.

FIG. 8 illustrates a configuration of an egress port arbitrationimplemented in the present invention. According to FIG. 8, MMU 115 alsoincludes a scheduler 802 that provides arbitration across the eightclass of service queues 804 a-804 h associated with each egress port toprovide minimum and maximum bandwidth guarantees. It is noted that whileeight classes of service are discussed, other formulations of classes ofservice are also supported. Scheduler 802 is integrated with a set ofminimum and maximum metering mechanisms 806 a-806 h that each monitorstraffic flows on a class of service basis and an overall egress portbasis. Metering mechanisms 806 a-806 h support traffic shaping functionsand guarantee minimum bandwidth specifications on a class of servicequeue and/or egress port basis, wherein scheduling decisions by schedule802 are configured largely via traffic shaping mechanisms 806 a-406 halong with a set of control masks that modify how scheduler 802 usestraffic shaping mechanisms 806 a-806 h.

As shown in FIG. 8, minimum and maximum metering mechanisms 806 a-806 hmonitor traffic flows on a class of service queue basis and an overallegress port basis. Maximum and minimum bandwidth meters 806 a-806 h areused to feed state information to scheduler 802 which responds bymodifying its service order across class of service queues 804. Thenetwork device 100 therefore enables system vendors to implement aquality of service model by configuring class of service queues 804 tosupport an explicit minimum and maximum bandwidth guarantee. In anembodiment of the invention, metering mechanisms 806 a-806 h monitortraffic flow on a class of service queue basis, provides stateinformation regarding whether or nor a class of service flow is above orbelow a specified minimum and maximum bandwidth specification, andtransmits the information into scheduler 802 which uses the meteringinformation to modify its scheduling decisions. As such, meteringmechanisms 806 a-806 h aid in partitioning class of service queues 804into a set of queues that have not met the minimum bandwidthspecification, a set that have met its minimum bandwidth but not itsmaximum bandwidth specification and a set that have exceeded its maximumbandwidth specification. If a queue is in the set that have not met itsminimum bandwidth specification and there are packets in the queue,scheduler 802 services the queue according to the configured schedulingdiscipline. If a queue is in the set that have met its minimum bandwidthspecification but has not exceeded it maximum bandwidth specificationand there are packets in the queue, scheduler 802 services the queueaccording to the configured scheduling discipline. If a queue is in theset that have exceeded its maximum bandwidth specification or if thequeue is empty, scheduler 802 does not service the queue.

The minimum and maximum bandwidth metering mechanisms 806 a-806 h may beimplemented using a simple leaky bucket mechanism which tracks whetheror not a class of service queue 804 has consumed its minimum or maximumbandwidth. The range of the minimum and maximum bandwidth setting foreach class of service 804 is between 64 kbps to 16 Gbps, in 64 kbpsincrements. The leaky bucket mechanism has a configurable number oftokens “leaking” out of buckets, each of which is associated with one ofqueues 804 a-804 h, at a configurable rate. In metering the minimumbandwidth for a class of service queue 804, as packets enter the classof service queue 804, a number of tokens in proportion to the size ofthe packet is added to a respective bucket, having a ceiling of buckethigh threshold. The leaky bucket mechanism includes a refresh updateinterface and a minimum bandwidth which defines how many tokens are tobe removed every refresh time unit. A minimum threshold is set toindicate whether a flow has satisfied at least its minimum rate and afill threshold is set to indicate how many tokens are in leaky bucket.When the fill threshold rises above minimum threshold, a flag whichindicates that the flow has satisfied its minimum bandwidthspecification is set to true. When fill threshold falls below minimumthreshold, the flag is set to false.

After metering mechanisms 806 a-806 h indicate that the maximumbandwidth specified has been exceeded high threshold, the scheduler 802ceases to service the queue and the queue is classified as being in theset of queues that have exceeded it maximum bandwidth specification. Aflag is then set to indicate that the queue has exceeded its maximumbandwidth. Thereafter, the queue will only receive service fromscheduler 802 when its fill threshold falls below high threshold and theflag indicating that it has exceeded its maximum bandwidth is reset.

Maximum rate metering mechanism 808 is used to indicate that the maximumbandwidth specified for a port has been exceeded and operates in thesame manner as meter mechanisms 806 a-806 h when the maximum totalbandwidth has been exceeded. According to an embodiment of theinvention, the maximum metering mechanism on a queue and port basisgenerally affects whether or not queue 804 or a port is to be includedin scheduling arbitration. As such, the maximum metering mechanism onlyhas a traffic limiting effect on scheduler 802.

On the other hand, minimum metering on a class of service queue 804basis has a more complex interaction with scheduler 802. In oneembodiment of the invention, scheduler 802 is configured to support avariety of scheduling disciplines that mimic the bandwidth sharingcapabilities of a weighted fair queuing scheme. The weighted fair queuescheme is a weighted version of packet based fair queuing scheme, whichis defined as a method for providing “bit-based round robin” schedulingof packets. As such, packets are scheduled for access to an egress portbased on their delivery time, which is computed as if the scheduler iscapable of providing bit-based round robin service. A relative weightfield influences the specifics of how the scheduler makes use of theminimum metering mechanism, wherein the scheduler attempts to provide aminimum bandwidth guarantee.

In one embodiment of the invention, the minimum bandwidth guarantee is arelative bandwidth guarantee wherein a relative field determines whetheror not scheduler 802 will treat the minimum bandwidth metering settingsas a specification for a relative or an absolute bandwidth guarantee. Ifthe relative field is set, the scheduler treats minimum bandwidth 806setting as a relative bandwidth specification. Scheduler 802 thenattempts to provide relative bandwidth sharing across backlogged queues804.

FIG. 9 provides a functional illustration of the multi-part parser 900.The multi-part parser is incorporated into the deep parser 540 in someembodiments of the present invention. The multi-part parser is formedfrom a number of parsing blocks 910, 920, etc., where each block isdedicated to parsing particular sections of an incoming packet. Eachblock is designed to start parsing from a zero offset, such that theparsed section output from one block are provided to the next block withfields that the block expects at the zero position. Thus, if one blockis dedicated to parsing tunnel values and the next is dedicated to parselayer 3 fields, then the first block will parse its own fields andprovide the parsed section to the next block without tunnelencapsulation. Since the block parsing is cumulative, subsequent blocksdo not need to search the packet header for relevant fields.Additionally, this allows for the functions of the individual blocks tobe streamlines

In specific embodiments, data is supplied 901 to the first stage 910parses layer 2 values and passes 915 the parsed section to the secondstage 920 to parse tunnel values, including IP or MPLS values.Thereafter, layer 3 values may be parsed by the third stage 930 and thefourth stage 940 parsing layer 4 values. After a final stage, therelevant and/or requested field values are output 975 for search,modification or substitution. Additionally, other parsing blocks may beused, including a de-encapsulation engine. The number of blocks is notlimited, however, to four or five, but the number of blocks that shouldbe used is related to the overall parsing requirements.

Also illustrated in FIG. 9 is the communication 918 between the blocks.This interaction allows for the multi-part parser to be response tospecific circumstance. One particular communication that may be used isfor the parsing of the next block to be skipped since it may not beneeded. An example might occur when it is initially decided that thede-encapsulation block should act on the packet section, but duringanother processing step, it is discovered that the packet is not an IPtunnel, for example, but rather IP over IP, so that the packet sectionneed only be parsed for IPv4 values.

The foregoing description has been directed to specific embodiments ofthis invention. It will be apparent, however, that other variations andmodifications may be made to the described embodiments, with theattainment of some or all of their advantages. Therefore, it is theobject of the appended claims to cover all such variations andmodifications as come within the true spirit and scope of the invention.

1. A network device for processing data on a data network, the networkdevice comprising: a plurality of ports, configured to receive data froma data network and to send processed data to the data network; a memorymanagement unit, in communication with and controlling memory externalto the network device, configured store data on and retrieve data fromthe memory; and a multi-part parser, in communication with the pluralityof ports and the memory management unit, configured to parse the datareceived; wherein the multi-part parser comprises several parsing blocksconfigured to serially parse the data, with each block designated toparse particular values and where each block but a first block receivesparsed data from a prior block with fields of the particular values at azero offset position.
 2. The network device according to claim 1,wherein a number of the several parsing blocks comprises four parsingblocks.
 3. The network device according to claim 2, wherein the fourparsing blocks comprises parsing blocks dedicated to parsing layer 2,layer 3 and layer 4 fields.
 4. The network device according to claim 1,wherein the several parsing blocks are connected by inter-communicationlines, where each block but the first block can be requested to omit itsparsing through a signal sent by the inter-communication lines.
 5. Thenetwork device according to claim 1, wherein one of the plurality ofports comprises a higher speed port and higher speed data received overthe higher speed port is parsed by a separate parser.
 6. The networkdevice according to claim 1, wherein each block of the several parsingblocks has access to a single search engine.
 7. The network deviceaccording to claim 1, wherein the one of the several parsing blocks isdedicated to de-encapsulate a received data packet.
 8. A method forprocessing data in a network device, the method comprising: receivingdata at a plurality of ports of a network device; parsing the data by amulti-part parser; storing the data by the memory management unit in amemory external to the network device; retrieving the received data fromthe memory and modifying the received data, if needed, based ondetermined attributes to produce processed data; and forwardingprocessed data to an egress port of the plurality of ports; wherein theparsing the data comprises serially parsing the data through severalparsing blocks, with each block designated to parse particular valuesand where each block but a first block receives parsed data from a priorblock with the fields of particular values at a zero offset position. 9.The method according to claim 8, wherein the serially parsing the datacomprises serially parsing the data through four parsing blocks.
 10. Themethod according to claim 9, wherein the four parsing blocks comprisesparsing blocks dedicated to parsing layer 2, layer 3 and layer 4 fields.11. The method according to claim 8, further comprising receiving asignal sent by inter-communication lines by one parsing block from aprior parsing block to omit parsing by the one parsing block.
 12. Themethod according to claim 8, wherein each block of the several parsingblocks has access to a single search engine.
 13. The method deviceaccording to claim 8, wherein the one of the several parsing blocks isdedicated to de-encapsulate a received data packet.
 14. A network devicefor processing data, the network device comprising: port means forreceiving data and forwarding processed data to an egress port; parsingmeans for parsing the data by a multi-part parser; memory means forstoring the data received by a memory management unit in a memoryexternal to the network device and retrieving the stored data; andmodifying means for modifying retrieved, stored data, based ondetermined attributes to produce processed data; wherein the parsingmeans comprises means for serially parsing the data through severalparsing blocks, with each block designated to parse particular valuesand where each block but a first block receives parsed data from a priorblock with fields of the particular values at a zero offset position.15. The network device according to claim 14, wherein the means forserially parsing the data comprises means for serially parsing the datathrough four parsing blocks.
 16. The network device according to claim14, further comprising lookup means for performing a lookup search oftables to determine the attributes of the received data.